Allow workspace and status filter to be negatable - #95023

@aimane-chnaif Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

@aimane-chnaif let's merge the text filter validation PR first, so we can resolve some of the type/lint error here.

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
• I checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
• I verified tests pass on all platforms & I tested again on:
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Knip check failed

Fixed

@aimane-chnaif back to you

Bug: empty space on mobile when only negated filter applied

That's happening on stg/prod too and will be fixed in the first PR

Please merge main

That's happening on stg/prod too and will be fixed in the first PR

what is repro step in stg/prod?

what is repro step in stg/prod?

Just type any filter with - prefix on the search router (e.g., -category:Advertising).

Please merge main

Done

🚧 JS00001 has triggered a test Expensify/App build. You can view the workflow run here.

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #95023.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-2880e10be9c-fbc55b5-218d6e9464304c20bbb326202daf6ace9278b7fc/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-2880e10-fbc55b5-a2aa1792c0981d50822b48a5096cf938f941bcc5/index.html

Web 🕸️
https://95023.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

🚀 Deployed to staging by https://github.com/JS00001 in version: 9.4.34-0 🚀

🤖 I reviewed the changes in this PR against the help site articles under docs/articles and no help site changes are required.

Why

This PR extends the existing - (negation/exclusion) capability to the workspace: and status: search filters. It's front-end only — the linked issue (#93208) confirms "negation is already supported by search" and "No changes to search syntax, query parsing, or the back end." The grammar change just reclassifies status from a special default key into a standard filter so it can be negated; the - prefix syntax itself is unchanged.

The relevant article, Use Search Operators to Filter and Analyze, already covers this behavior generically:

• It documents the exclusion operator: "Use - to exclude results: -has:receipt."
• It already lists both workspace: and status: as supported filters.

So -workspace:"My workspace 1" and -status:draft are already described by the existing generic negation rule plus the existing filter list — this PR adds no new operator syntax or user-facing terminology that the help site needs to document.

The visual is / is not filter-configuration toggle from the broader initiative is not documented in the help site today, and this single PR doesn't introduce it in a way that warrants a docs change on its own.

@bernhardoj, does this match your understanding? If you feel the search operators article should explicitly call out which filters support negation (or document the new is / is not toggle UI as part of the wider #93208 rollout), let me know and I'll open a draft help site PR.

Deploy Blocker #96057 was identified to be related to this PR.

Deploy Blocker #96074 was identified to be related to this PR.

🚀 Deployed to production by https://github.com/roryabraham in version: 9.4.34-14 🚀

🚀 Deployed to production by https://github.com/roryabraham in version: 9.4.34-14 🚀

Bundle Size Analysis (Sentry):

• Android